Form-based user interface for controlling messaging

ABSTRACT

An integrated messaging system for performing various types of messaging across different types of networks, including integrated user interfaces and administrator interfaces. Embodiments include a communication server that couples among networks of different types, and an interface module that couples to the communication server. The interface module may be hosted on a messaging server of a network. The interface module pulls various user information from the messaging server, including information relevant to at least the network that includes the messaging server. A cache couples to the communication server and to the interface module to hold information from the communication server and/or the user information pulled from messaging server. The interface module directs a message from the messaging server and/or the cache to at least one device on the networks using the user information.

CROSS-REFERENCE

This application is related to the following United States patentapplications:

Integrated Multi-Media Communication System, U.S. application Ser. No.11/053,271, invented by Jens Skakkebaek, Heine Frifeldt, and AnthonyShaffer, filed Feb. 7, 2005;

Controlling Messaging Actions Using Form-Based User Interface, U.S.application Ser. No. 11/053,146, invented by Heine Frifeldt, AnthonyShaffer, and Willem R. B. Potze, filed Feb. 7, 2005;

Caching Message Information In An Integrated Communication System, U.S.application Ser. No. 11/053,147, invented by Shahriar Vaghar, Yang Wang,and Jens Skakkebaek, filed Feb. 7, 2005;

Distributed Cache System, U.S. application Ser. No. 11/015,411, inventedby Shahriar Vaghar, Yang Wang, and Jens Skakkebaek, filed Feb. 7, 2005;

Caching User Information In An Integrated Communication System, U.S.application Ser. No. 11/053,272, invented by Jens Skakkebaek, Willem R.B. Potze, and Heine Frifeldt, filed Feb. 7, 2005;

Integrating Messaging Sewer Directory Service With Communication SystemVoice Mail Message Interface, U.S. application Ser. No. 11/053,709,invented by Heine Frifeldt, David Forney, and Anthony Shaffer, filedFeb. 7, 2005;

Improved Message Data Access In Multi-Media Communication System, U.S.application Ser. No. 11/053,736, invented by Jens Skakkebaek and HeineFrifeldt, filed Feb. 7, 2005;

System And Method For Voicemail Privacy, U.S. application Ser. No.11/053,054, invented by Anthony Shaffer, Heine Frifeldt and DavidForney, filed Feb. 7, 2005;

Networked Voicemail, U.S. application Ser. No. 11/053,425, invented byDavid Forney, Jens Skakkebaek, Heine Frifeldt, and Anthony Shaffer,filed Feb. 7, 2005;

Extensible Diagnostic Tool, U.S. application Ser. No. 11/053,270,invented by David Forney, Heine Frifeldt, and Anthony Shaffer, filedFeb. 7, 2005;

System And Method For Providing Data On Voicemail Appliance, U.S.application Ser. No. 11/053,538, invented by Jens Skakkebaek and LutzBirkhahn, filed Feb. 7, 2005;

Integrated Voice Mail User/Email System User Setup in IntegratedMulti-Media Communication System, U.S. application Ser. No. 11/053,539,invented by Heine Frifeldt, David Forney, and Anthony Shaffer, filedFeb. 7, 2005; and

System And Method For Providing Code On Voicemail Appliance, U.S.application Ser. No. 11/053,376, invented by Jens Skakkebaek and LutzBirkhahn, flied Feb. 7, 2005.

TECHNICAL FIELD

The disclosure herein relates generally to communication systems, andmore particularly to integrated communication and messaging systems.

BACKGROUND

As methods of communication continue to proliferate, enterprisescontinue to desire integrated systems for handling all aspects ofmulti-media communication for enterprise users. An enterprise can be anycollection of users of communication media having some common purpose,but a typical example is a company with one or more sites and somenumber of employees who are users of communication media. Communicationmedia include electronic mail (“email”) messaging, Short MessagingService (“SMS”) messaging, voice messaging, and more. Users receive andsend messages over a variety of wired and wireless networks via avariety of devices, such as desktop computers, wired phones, wirelessdevices (e.g., phones and personal digital assistants (“PDAs”)), andmore.

Enterprises currently have the ability to centralize and manage emailmessaging using commercially available groupware that centrally storesinformation about all of the users and their messages. Enterprises alsohave the ability to centrally manage traditional voice messaging using aPrivate Branch Exchange (“PBX”). However, the systems for managing emailmessaging and the systems for managing voice mail messaging are not atall well integrated. For example, when a new user is added to theenterprise, a system administrator for the enterprise sets up the userin the email system using the groupware application and its set methods,data and protocols. In addition, a different administrator specializingin telephony must set up the user in the voice messaging system usingdifferent methods, data and protocols. Voice data and email data aretypically stored in separate databases. Both initial user setup andupdating user information are complicated by the fact that the email andvoice systems are so distinct.

The management of and access to the voice mail message information andemail information in the enterprise is also complicated by the currentlack of integration of the two (voice and email) systems. There arevarious challenges to be overcome if one were to attempt to integratethe two systems.

INCORPORATION BY REFERENCE

All publications and patent applications mentioned in this specificationare herein incorporated by reference to the same extent as if eachindividual publication or patent application was specifically andindividually indicated to be incorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system that includes an integratedcommunication system (“ICS”), under an embodiment.

FIG. 2 is a flow diagram for providing integrated communicationprocesses using the ICS, under an embodiment.

FIG. 3 is a block diagram of example information flows in a system thatincludes the ICS, under an embodiment.

FIG. 4 is another flow diagram for providing integrated communicationprocesses using the ICS, under an embodiment.

FIG. 5 is a block diagram of an enterprise network system that includesa communication server and Interface Module (“IM”) of an ICS, under anembodiment.

FIG. 6 is a block diagram of an enterprise network system that includesthe ICS, under an embodiment.

FIG. 7 is a block diagram that shows interactions between the IM andcomponents of a messaging server (“MSERV”) environment, under anembodiment.

FIG. 8 is an information flow for routing and accessing voice mailmessages via the ICS when the MSERV is in an online state, under anembodiment.

FIG. 9 is an alternative information flow for routing and accessingvoice mail messages via the ICS when the MSERV is in an online state,under an embodiment.

FIG. 10 is an information flow for routing and accessing voice mailmessages via the ICS when the MSERV is in an offline state, under anembodiment.

FIG. 11 is a block diagram of a system that includes the ICS with aForm-Based User Interface (“FBUI”), under an embodiment.

FIG. 12 is a sample FBUI as displayed on a client device, under anembodiment.

FIG. 13 is a block diagram of a system that uses a form-based interfacetransferred in a first type of message for controlling actions on asecond type of message, along with the corresponding information flows,under an embodiment.

FIG. 14 is a selection popup the ICS provides during execution of thePlay on Phone action, under an embodiment.

FIG. 15 is a status popup the ICS provides during execution of the Playon Phone action, under an embodiment.

FIG. 16 is another status popup the ICS provides during execution of thePlay on Phone action, under an embodiment.

FIG. 17 is an information flow in a system that includes an ICSsupporting Play on Phone operations, under an embodiment.

In the drawings, the same reference numbers identify identical orsubstantially similar elements or acts. To easily identify thediscussion of any particular element or act, the most significant digitor digits in a reference number refer to the Figure number in which thatelement is first introduced (e.g., element 110 is first introduced anddiscussed with respect to FIG. 1).

DETAILED DESCRIPTION

Integrated multi-media communication systems and methods are providedbelow. These communication systems and methods, collectively referred toherein as “integrated communication systems” or “ICS,” integratedifferent types of messaging so that a user of the ICS can accessmultiple types of messages (e.g., voice mail messages, electronic mail,email messages, instant messaging messages, SMS (Short Messaging System)messages, MMS (Multimedia Messaging System) messages, etc. with a singlemessage interface. In providing integrated messaging functionality via asingle message interface, the ICS of an embodiment relieves thedependency of a voice mail system, for example, by providing users withaccess to voice mail messages and capabilities of the voice mail systemthrough the local groupware applications and email messaging system.

The ICS generally includes a communication server, a cache system, andan interface module. The ICS integrates with a messaging andcollaboration system and the corresponding groupware applications in anetwork environment for example. In providing integrated messagingcapabilities, the communication server and interface module function toroute a call received from a caller to a user and, in the event the useris not available, to receive and route a voice mail message left by thecaller. The ICS uses caching processes during the receiving and routingof voice mail messages that provide users with fast access to voice mailmessages, user information and contact information. Using cachingprocess, the ICS also provides access to the voice mail messaging systemduring periods when the messaging and collaboration system is offline.The ICS also leverages the storage capability of the messaging andcollaboration system to eliminate the need for a separate voice maildatabase.

The message interface of the ICS includes a form-based interface for usein retrieving voice mail messages and controlling actions taken on voicemail messages received in the enterprise network system. This form-basedinterface enables a user to retrieve and take various actions on voicemail messages using data of a form provided to the user's client deviceby the enterprise network email system. Use of the form-based interfacethus provides users with access to the integrated messaging functionsoffered by the ICS without a requirement to install or run a dedicatedclient application on the user's client device.

In the following description, numerous specific details are introducedto provide a thorough understanding of, and enabling description for,embodiments of the ICS. One skilled in the relevant art, however, willrecognize that these embodiments can be practiced without one or more ofthe specific details, or with other components, systems, etc. In otherinstances, well-known structures or operations are not shown, or are notdescribed in detail, to avoid obscuring aspects of the disclosedembodiments.

FIG. 1 is a block diagram of a system 10 that includes an integratedcommunication system (“ICS”) 100, under an embodiment. ICS 100 includesa communication server 110, an interface module (“IM”) 120, and a cachesystem 130 (also referred to as the “cache”), but is not so limited.Communication server 110 couples to components of any number of networks150 and 160 using any of a variety of communication protocols, wherenetworks 150 and 160 may be of the same or of different types. Networks150 and 160 allow for information transfers between various clientdevices 170 and 199, also referred to as user devices 170 and 199.

IM 120 of ICS 100 couples to transfer information or data withcommunication server 110. Additionally, IM 120 couples to transferinformation with one or more components of a messaging server 140, wheretransferring information includes one or more of pulling, receiving,retrieving, polling, transmitting, and pushing operations, to name afew. As an example of an information transfer between IM 120 andmessaging server 140, IM 120 pulls user information from messagingserver 140 and makes the pulled user information available to othercomponents of ICS 100, wherein the user information includes informationrelevant to at least network 150.

The components of messaging server 140 may include for example one ormore processors 142, also referred to as “central processing units” or“CPUs,” and one or more databases 144 coupled to CPU 142. In anembodiment, IM 120 may be hosted on or running under control ofmessaging server 140, but is not limited to this configuration. Further,messaging server 140 may be a component of network 150 that hostscommunication server 110, but is not so limited. For example, messagingserver 140 may be hosting a groupware application (e.g., MicrosoftExchange, LotusNotes, etc.) of an enterprise network 150.

Cache 130 couples to communication server 110 and communicates totransfer information with one or more of communication server 110, IM120, and one or more components of messaging server 140, as describedbelow. Cache 130 may also couple to additional components (not shown) ofnetwork 150.

As an example of information transfers between cache 130 andcommunication server 110, cache 130 may receive caller information(e.g., voice mail messages, caller identification, etc.) from clientdevices 199 via communication server 110. An example of informationtransfers between cache 130 and messaging server 140 includes transfersin which cache 130 receives user information from messaging server 140,where the user information may be routed from messaging server 140 viaIM 120 and/or communication server 110. Another example of informationtransfers between cache 130 and messaging server 140 includes transfersin which messaging server 140 receives information from cache 130 routedfrom cache 130 via communication server 110 and/or IM 120.

Examples of information transfers between cache 130 and IM 120 includetransfers of user information pulled from messaging server 140 by IM 120and directed to cache 130, and transfers in which IM 120 directs amessage from at least one of messaging server 140 and cache 130 to atleast one device on networks 150 and 160 using the user information.Cache 130 holds or temporarily stores the received information under theabove examples.

Networks 150 and 160 include various network components (not shown) ofone or more communication service providers or carriers, but are not solimited. Further, networks 150 and 160 and corresponding networkcomponents can be any of a number/combination of network types known inthe art for providing communications among coupled devices 170 and 199including, but not limited to, proprietary networks, local area networks(“LANs”), metropolitan area networks (“MANs”), wide area networks(“WANs”), backend networks, public switched telephone networks (“PSTN”),the Internet, and other public networks for example. Additionally,networks 150 and 160 may include hybrid networks that use a proprietarynetwork for some portion of the communications routing, for example,while using one or more different public networks for other portions ofthe communications routing.

Client devices 170 and 199 include communication devices liketelephones, cellular telephones, and radio telephones. Client devices170 and 199 also include processor-based devices like, for example,portable computers (“PC”), portable computing devices, personal digitalassistants (“PDA”), communication devices, cellular telephones, portabletelephones, portable communication devices, and user devices or units.Client devices can include so-called multi-modal devices, where the usercan interact with the device and/or the ICS through any form of inputand output, such as text input, speech recognition, text output,text-to-speech, graphics, recorded files and video. In such devices, thespeech recognition and text-to-speech generation may partly take placein the device and partly in the ICS. Sound and/or video may be generatedby the ICS by a continuous stream of sound and/or video data sent to thedevice. Client devices can include all such devices and equivalents, andare not limited to any particular type of communication and/orprocessor-based device. In an embodiment client devices 170 are clientdevices operating in a private network environment like an enterprisenetwork, while client devices 199 are client devices operating indifferent private network environments or under any number of publicnetworks.

FIG. 2 is a flow diagram for providing integrated communicationprocesses 200 using ICS 100, under an embodiment. Processes 200 includereceiving data streams from networks of different types, at block 202.The data streams may include a variety of data including, for example,audio or voice data. Further, the data streams may be received from anynumber of networks or client devices operating on the networks.Processes 200 further include generating messages at a communicationserver using information of the data streams, at block 204. Thegenerated messages may be any of a number of message types. Returning tothe above example in which the received data stream includes audio data,the generated message is a voice mail message, but is not so limited.Processes 200 also include transferring the messages, at block 206. Thetransferring operation includes for example caching information of themessages in the ICS cache and/or forwarding the messages to a messagingserver.

Continuing, processes 200 include pulling user information from amessaging server coupled to the ICS, at block 208, as described above.The user information includes information relevant to users of at leastthe network hosting the ICS, but is not so limited. Processes 200 alsoinclude caching pulled user information from the messaging server, atblock 210. Additionally, processes 200 include use of the userinformation of the cache to direct a message from at least one of themessaging server and the cache to one or more client devices on any ofthe networks, at block 212.

The ICS of an embodiment integrates different types of messaging so thata user of the ICS can access all of the message types (e.g., voice mailmessages, electronic mail or email messages, etc.) with a single messageinterface (also referred to as a “user interface” or “UI”). In providingintegrated messaging functionality via a single message interface, theICS of an embodiment relieves the dependency on a voice mail system witha dedicated voicemail and user database, for example, by providing userswith access to voice mail messages and capabilities of the voice mailsystem through the local email messaging system.

FIG. 3 is a block diagram of example information flows 300 in a system30 that includes ICS 100, under an embodiment. The system also includesa messaging server 140 and any number of client devices 170 that coupleto ICS 100. In addition, ICS 100 couples to a communications network160. ICS 100, messaging server 140, and client devices 170 may be hostedunder a network 150, but are not so limited. System 30 is shown with oneeach of ICS 100, messaging server 140, and client device 170 forpurposes of this description, but may include any number of each of ICS100, messaging server 140, and client device 170 coupled in anycombination. System 30 may also couple to one or more other systems (notshown) or networks via any number of backend couplings (not shown)

Components of ICS 100 include a communication server and an interface(not shown). The interface of ICS 100 may run under control of messagingserver 140, as described above, but is not so limited. Information flow300 begins when, in response to receiving data streams from networks 160of different types, ICS 100 generates a first message 302 and transfersfirst message 302 to messaging server 140 via a communication withmessaging server 140. First message 302 may be a voice mail message(“Voice Mail Type” or “VMT”) but is not limited to this type of message.For purposes of the description herein, a voice mail message is left bya “caller” to the ICS. For example, in an embodiment where MicrosoftExchange is the messaging server 140, the VMT may be implemented using“Message Class” and/or “Message Type” fields associated with messages inMicrosoft Exchange.

Following or simultaneous with receipt of first message 302, themessaging server 140 detects or identifies a type of first message 302using information of the first message and generates a second message312. Second message 312 is of a different type from that of firstmessage 302, and includes information of first message 302. Secondmessage 312 may for example be an email message but is not limited tothis type of message. Second message 312 is transferred to a clientdevice 170 via a communication with client device 170, where thecommunication uses a communication protocol of network 150.

Responsive to receipt of second message 312, client device 170determines a type of the second message and requests form data 314 thatcorresponds to second message 312. Messaging server 140, in response tothe request for form data 314, transfers form data 314 to client device170 via the second coupling. One or more components of ICS 100 generateand/or provide form data 314 for storage in messaging server 140, andform data 314 is generated under the communication infrastructure ofnetwork 150. The form data may be displayed to the user using thecorresponding form.

Client device 170 uses form data 314 to view contents of second message312. The client device also uses form data 314 to establishcommunications with communication server 110 (of ICS 100) via a thirdcoupling. The communication protocol of the third coupling is differentthan the communication protocol of the second coupling, but is not solimited. An “embedded control” controls activation of the thirdcoupling. Furthermore, the client device allows a “user” using theclient device to direct actions 322 on first message 302 via the thirdcoupling with the ICS using the form data. For purposes of thedescription herein, a “user” is an individual with enabled capability touse functions within the ICS.

As an example under information flows 300, FIG. 4 is a flow diagram forintegrated communication processes 400 using ICS 100, under anembodiment. Processes 400 include transferring a first message to amessaging server from a communication server via a first coupling, atblock 402. Processes 400 also include generating a second message at themessaging server in response to a type of the first message andtransferring the second message to a client device via a secondcoupling, at block 404. The second message may be of a different typethan the first message and includes data of the first message. Processes400 further include transferring to the client device form data thatcorresponds to the first message, at block 406. Additionally, processes400 include establishing a third coupling between the client device andthe communication server using the form data, at block 408. Moreover,processes 400 include directing actions on the first message from theclient device using the form data, the actions directed via the thirdcoupling, at block 410.

The ICS of an embodiment integrates messages of different types toenable a user to access a number of message types through components ofthe ICS. Thus, an application of the ICS of an embodiment is as asubstitute for a voice mail system in an enterprise network, where theICS enables a user to receive and/or take action on voice mail messagesusing the enterprise email system.

FIG. 5 is a block diagram of an enterprise network system 500 thatincludes a communication server 110 and IM 120 of an ICS, under anembodiment. Communication server 110 couples to at least one messagingserver 140 via IM 120. IM 120 runs under messaging server 140, but isnot limited to running under this server. Messaging server also couplesto one or more databases 144. Messaging server 140 of an embodimentsupports the messaging capabilities of enterprise network system 500using a groupware application (e.g., Microsoft Exchange) (not shown)along with other applications as appropriate to the size and type ofenterprise network system 500. Messaging server 140, database 144, andgroupware application (not shown) may be referred to as collectivelyforming a “messaging environment.”

Communication server 110 couples to any number of client devices 199external to enterprise network 500 via one or more networks (not shown),as described above with reference to FIG. 1. Similarly, communicationserver 110 couples to any number of client devices 170 local toenterprise network 500.

Communication server 110 includes an operating system 518 as well asnumerous components or subsystems. These components include but are notlimited to one or more Voice Applications 512, an Execution Engine 514,and any number of Mobile Application Modules 516, as described below, orany other type of application module.

FIG. 6 is a block diagram of an enterprise network system 600 thatincludes an ICS, under an embodiment. The ICS includes a communicationserver 610 as described above, also referred to as a “MessagingCommunication Server” or “MCS.” The MCS may be highly scalable.According to an embodiment of the invention, the MCS may be configuredas a modular “appliance” that is essentially self-contained, and may be,for example, encased in a stackable, “pizza-box” style server. The ICSalso includes IM 620 (also referred to herein as the “IM”) and aManagement Console 660. The IM, which in one embodiment runs undercontrol of a messaging server 640 (also referred to herein as “MSERV640” or “MSERV”), couples to components of the MCS, the MSERV, and aDatabase 644 (also referred to herein as a “Database”) in a number ofsequences as described herein and as appropriate to enterprise networksystem 600. The IM also couples to MCS Management Console 660. The MCSand the MSERV couple to the LAN for communication with other components(not shown) of enterprise network system 600.

The MCS of an embodiment includes an “Operating System” along with an“Execution Engine,” some number of “Voice Applications,” and some numberof “Mobile Applications.” The Operating System includes for example aLinux kernel with a journaling file system that provides integrity offile system tables and the data structure. The storage on the MCS may beconfigured as a RAID (Redundant Array of Independent Disks)configuration to provide high reliability access to software and data.The Operating System supports operations of numerous other components ofthe MCS as described below.

With regard to the Operating System, the MCS includes a “TelephonyInterface” that couples calls and connects callers and users to/from theMCS. The Telephony Interface couples call information to/from a privatebranch exchange (“PBX”) (not shown) for example, where the PBX is acomponent of enterprise network system 600. The Telephony Interfacecouples to the PBX using a variety of telephony integrations thatinclude one or more of analog, Simplified Message Desk Interface(“SMDI”), T1/E1, Voice over Internet Protocol (“VOIP”), and Digital SetEmulation (“DSE”) signals, but may couple using other signals/signalingprotocols. When receiving a call from the PBX, for example, the MCSreceives data of an incoming call from the PBX, where the data includescalled party information, a reason for transfer of call (e.g., calledparty line busy, no answer by called party, called party using callforwarding, etc.), and calling parting information (caller ID, etc.).

A “Driver” couples information received at the Telephony Interface tothe “Telephony Services” component of the MCS. The Driver may performlow level signaling and/or data conversion as appropriate to thereceived signals. The Telephony Services include one or more componentsfor use in processing the received signals. These components include,for example, voice processing, switching/control, and PBX signaling, butare not limited to these components.

The MCS of an embodiment includes at least one “Voice Browser” that,when the MCS receives a call, receives voice information of the call.The Voice Browser controls the use of automatic speech recognition(“ASR”) for speech recognition and DTMF recognition. The Voice Browserof an embodiment couples to a cache or other temporary store that holdsvoice recordings and/or name grammars (“Voice Recordings/Grammars”) (thename grammars are cached after being generated from names in a userlist, as described below). The ASR may use information of the namegrammars. Further, the Voice Browser controls the use of text-to-speech(“TTS”) as well as the play of any number of pre-recorded prompts (e.g.,WAVE format files). The Voice Browser uses voice extensible markuplanguage (“VXML”) but is not limited to this protocol. Alternativeembodiments of the MCS may not include the Voice Browser. As analternative to a Voice Browser, the MCS may directly communicate with,or use other software or processes, for communication between the voiceapplication and the Telephony Services and/or Driver.

The Virtual Machine, Voice Applications, and Execution Engine form ahierarchical state machine framework in which the Virtual Machine runs anumber of APIs and modules. Consequently, the Voice Applications caninclude one component controlling the user interfaces (“UI”) to the MCS,and another component handling lower-level communications with themodules. Use of a loose coupling between the modules and the VoiceBrowser provided by the state machine framework allows independencebetween the languages used in the different modules and the VoiceBrowser. The state machine framework may receive hypertext transportprotocol (“HTTP”) requests from the Voice Browser, for example, andgenerate VXML or Speech Application Language Tags (“SALT”) (SALT extendsexisting mark-up languages such as hypertext markup language (“HTML”),extensible hypertext markup language (“XHTML”), and extensible markuplanguage (“XML”), and enables multimodal and telephony-enabled access toinformation, applications, and web services from devices like PCs,telephones, and PDAs for example).

The Voice Applications of an embodiment include a number of componentsincluding an automatic attendant, a caller interface, a user interface,and a system main menu, but may include other types of voiceapplications. The automatic attendant is speech enabled, but may be dualtone multi-frequency (“DTMF”)-enabled. The automatic attendant, whichcan be enabled or disabled, uses information of contact lists (e.g.,User List) in the Cache.

The Voice Applications also include at least one voice mail application.The voice mail application uses information of the Cache (e.g., UserList, Global Address List, Public Folders, Personal Contact Folders) inoperations that include sending a new voice mail and/or forwarding areceived voice mail. The voice mail application also uses Cacheinformation in support of voice mail networking in which voice mails andcorresponding information are exchanged with groupware applications ofenterprise network system 600, as described below.

The voice mail application couples to the MCS state machine frameworkdescribed above via one or more application programming interfaces(“API”). The APIs handle the different data formats/types in use byenterprise network system 600 (e.g., greeting data, PIN (PersonalIdentification Number) code data, voice mail message data, systemparameters, etc.). Similarly, the Cache also couples to the statemachine framework, where the Cache includes one or more of local cacheand distributed cache. Therefore, communications among the voice mailapplication, the Cache, and the MSERV take place via the state machineframework and the APIs as appropriate to the state (e.g., offline,online) of the MSERV.

In addition to the Voice Applications, the modules running under theVirtual Machine of an embodiment include Mobile Applications. The MobileApplications provide access to user information via mobile devices,where the access may include transferring information of email,calendar, and/or contacts to a user's mobile client device via anelectronic message (e.g., SMS, MMS, and/or pager).

The MCS also includes an “Administration/Configuration” manager. TheAdministration/Configuration manager provides access to and control of aunified configuration file of the MCS. The Administration/Configurationmanager uses information of the unified configuration file to provideseparate Configuration Files to one or more of the components of the MCSas appropriate. The unified configuration file can be copied from theMCS and stored for backup purposes. Additionally, a predefinedconfiguration file may be uploaded to the MCS to provide the appropriateconfiguration for the MCS. A browser interface to theAdministration/Configuration manager allows remote access to the MCS.

The MCS also includes a “Self Maintenance Supervisor” or reliabilityserver that monitors MCS components and restarts failed processes whennecessary, for example. In addition, the MCS also includes “SecurityRestrictions” for use in controlling MCS/port security.

As described above, the MCS of an embodiment interfaces with the MSERVvia the IM. The MCS communicates with the IM via the Groupware Connectorfor example, but is not so limited. The Groupware Connector of anembodiment includes a “Web server,” but is not so limited. The MSERVfunctions as a messaging and collaboration server. The IM is aninterface that runs under the MSERV in one embodiment to providecommunications and information transfers between components of the MCSand components of the MSERV. In other embodiments, the IM may run undercontrol of the MCS, for example. The IM includes and/or couples withManagement Console 660 as well as with a diagnostics component(“Diagnostics Component”) and/or a run time component (“RTC”) (notshown).

Management Console 660 supports access to the MCS by a systemadministrator of enterprise network system 600 for purposes of managinguser access. Consequently, Management Console 660 allows a systemadministrator to enable new users with integrated messagingfunctionality of the ICS and administer and monitor one or more MCSs.

The Diagnostics Component of the IM supports on-the-fly diagnosticsgathering, computing, and/or compiling of pre-specified diagnosticsinformation or parameters from the MSERV. In this manner the MCS mayprovide diagnostics information and a user may provide dynamicallyupdateable diagnostics information.

The RTC translates communications between components of the MCS andcomponents of the MSERV. As an example the RTC may be used to retrieveuser information from the directory service (e.g., Active Directory) ofa groupware application in response to a request from the MCS, asdescribed below. Communications between the RTC and components of theMCS use for example XML and Web Services. Communications between the RTCand the MSERV may use one or more APIs of the MSERV (e.g., MAPI,Collaboration Data Objects (“CDO”), Web Distributed Authoring andVersioning (“WebDAV”), etc.).

The MSERV of an embodiment represents a messaging and collaborationserver. The messaging and collaboration server includes a groupwareapplication that runs on one or more servers and enables users via localclient devices to send and/or receive electronic mail and other forms ofinteractive communication through computer networks. The MCS of anembodiment interoperates with groupware applications that include, butare not limited to, Microsoft Exchange Server, but alternativeembodiments may use other types of messaging and collaboration servers.Therefore, the MCS of an embodiment interoperates with client deviceapplications (“client applications”) such as Microsoft Outlook, as wellas with other email client applications (e.g., Microsoft OutlookExpress).

The MSERV sends and receives email messages through what is commonlyreferred to as a client device such as a personal computer, workstation,or a mobile device including mobile phones or PDAs. The client devicetypically connects to the LAN, which may include any number and/orcombination of servers or mainframe computers where the email mailboxesand public folders are stored. The centralized servers connect tonumerous other types of networks (e.g., private or proprietary, and theInternet) to transmit and receive email messages to other email users.Consequently, the MCS uses the MSERV for storing and forwarding emailmessages in an embodiment.

The MSERV also couples to a directory service (not shown), which is adatabase of information on each user account in the enterprise networksystem. Access to the directory service may use for example aLightweight Directory Access Protocol (“LDAP”).

With regard to client device access functionality, the MSERV providesintegrated collaborative messaging features such as scheduling, contact,and task management capabilities. As an example MSERV configuration,when the MSERV is Microsoft Exchange, the MSERV runs on a version of theMicrosoft Windows Server operating system. A version of Microsoft OfficeOutlook runs on Windows-based local client devices and communicates withthe MSERV through the messaging application programming interface(“MAPI”) protocol. The MSERV also accommodates other client deviceaccess by supporting one or more of Post Office Protocol 3 (“POP3”) andInternet Message Access Protocol 4 (“IMAP4”) protocols as well assupport for Simple Mail Transfer Protocol (“SMTP”). Using this sameMSERV configuration example, the MCS of an embodiment, along withMicrosoft Outlook Web Access (a service in Microsoft Exchange)accommodates web browser-based access clients, also referred to as thinclients.

The MSERV collaboration features support information sharing amongusers. Collaborative scenarios include maintaining shared address liststhat all users can view and edit, scheduling meetings that includepeople and conference rooms by viewing associated free or busyschedules, the ability to grant other people, such as administrators,access to user mailboxes on behalf of the user.

As described above, the IM serves as an interface for the transfer ofinformation between components of the MCS and components of the MSERV.Transferring information includes for example pulling, receiving,retrieving, polling, transmitting, and pushing operations, to name afew. As an example of information transfers between the MCS and theMSERV, the IM pulls information from one or more components of the MSERVand makes the pulled information available to, for example, the MCSCache. The IM also pushes information from one or more components of theMCS to the MSERV.

In serving as an interface between the MCS and the MSERV, the componentsof the IM (e.g., RTC) translate communications between components of theMCS (e.g., Virtual Machine, Cache, etc.) and components of the MSERVenvironment. As an example the IM retrieves user information fromcomponents of the directory service (e.g., Active Directory) in responseto a request from the MCS/Cache.

Embodiments of the IM may include one or more of the followingcomponents: an RTC, a Management Console, a desktop component, messagingactions control component, Diagnostics Component and/or a messagewaiting indication component. The desktop component allows the user toconfigure aspects of the user's integrated messaging account, such asvoice message greetings, extended absence greeting, PIN code data, andpresence information. The messaging actions control component receivesand responds to user generated requests from the FBUI (defined herein)to take actions such as playing, replaying to and forwarding voicemessages, as well as calling the sender of a voice mail message. Themessage waiting indication component receives events from the user'smessage inbox folder and requests corresponding action from the PBX orother aspect of the telephony system, such turning on message waitingindicators on the user's device(s). The message waiting indicationcomponent may send notifications by way of SMS, MMS and/or pager.

FIG. 7 is a block diagram 700 that shows interactions between the IM andcomponents of the MSERV environment 740, under an embodiment. Thecomponents of MSERV environment 740 include the MSERV and one or moreDatabases as described above. The Database of an embodiment includes adirectory service 742.

Directory service 742 provides a location for storage of informationabout network-based entities, such as applications, files, and printersto name a few. Directory service 742 also stores information aboutindividuals, also referred to as users, and this information is referredto herein as “User Information.” As such directory service 742 providesa consistent way to name, describe, locate, access, manage, and secureinformation about individual resources in an enterprise networkenvironment. Directory service 742 uses the stored information to act asthe main switchboard of the enterprise network operating system and istherefore the central authority that manages the identities and brokersthe relationships between distributed resources of the enterprisenetwork, thus enabling the resources to work together. Directory service742 of an embodiment may be Microsoft Active Directory (“AD”), but isnot so limited.

In embodiments including AD, there is a user object stored in an ADDatabase for each enterprise user. For example, the user object forenterprise USER 2 is shown as USER 2 object 702. The user objectincludes many fixed attributes such as user name, user phone number,user mailbox location, and user email address.

The user object further includes a number of “Custom Attributes.” Thenumber of Custom Attributes is small, for example fifteen, compared tothe number of fixed attributes. The Custom Attributes are usable tostore information not provided for in the predefined fixed attributes.In one embodiment, a Custom Attribute stores user-specific data that isused by the Voice Applications. Examples of such user-specific datainclude a class of service (“COS”) for the user, a voice mail extensionfor the user, whether voice mail is enabled for the user, etc. The datais stored as a data stream in the Custom Attribute with a maximum sizeof 2048 bytes. In an alternative embodiment, the user-specific data thatis used by the Voice Applications is stored as individual data items infixed attributes by extending AD in a known manner.

The user mailbox location fixed attribute indicates where the user'semail mailbox is stored in the enterprise. In some large enterprises,there may be many MSERVs, each including a database storing many usermailboxes. As shown, the mailbox location fixed attribute points to USER2 mailbox 704 on an MSERV called MSERV 1.

User mailbox 704 stores email messages sent to the user, as well asoutgoing messages and other items, for predetermined periods of time. Inan embodiment, the messages can be of at least two types, one of whichis a “normal” message that is routinely accessible by the user. Anothermessage type is a “hidden” message that is not routinely accessible bythe user through the normal user email interfaces. In an embodiment, ahidden message is used to store data used by the Voice Applications. Incontrast to the data stored in the Custom Attribute, however, the datastored in the hidden message can be much larger than the 2048 byte limitof the custom attribute. In one embodiment, among the data stored in thehidden message are audio files stored as attachments to the hiddenmessage, such as a “busy” greeting for the user's voice mail mailbox, a“no answer” greeting for the user's voice mail mailbox, and a recordedname for the user's voice mail mailbox.

An example of the MCS accessing the MSERV environment 740 through IM 620is a phone caller calling the voice mail mailbox of USER 2 when USER 2is on the phone. The MCS transmits an action via IM 620 with a requestto “play busy greeting.” The transmission includes information to accessthe USER 2 object 702 fixed attributes to determine the user's emailmailbox location. In addition the transmission includes information toaccess the USER 2 object 702 Custom Attribute and to transfer thecontents of the Custom Attribute to the MCS via IM 620. When the user'semail mailbox is accessed, the hidden message is opened to transfer theappropriate audio file (“busy” greeting in this case) to the MCS forplaying over the phone to the caller. In many cases, it may not benecessary to transfer either the Custom Attribute or the audio file fromthe MSERV environment 740 because the current custom attributes andaudio file are cached on the MCS.

As described above, operations of the Voice Applications and the VirtualMachine couple the Cache and other components of the MCS to componentsof the MSERV via the IM. As such, the MCS and the IM support thetransfer of information between the Cache and backend network componentslike the MSERV and the database. This configuration providestransparency between the Voice Applications and data stored in thedatabase when using information of the database to support voice mailmessaging functions of the MCS, as described below.

The information transfers between the Cache and the MSERV along with useof the Custom Attributes and Hidden Messages as described above allowthe ICS to overcome the need for an external database to storeinformation stored by a typical voice mail system. This is because theinformation used by the MCS in providing voice mail message capabilitiesintegrated with the email messaging capabilities of the enterprisenetwork is pulled by the MCS from the MSERV via the IM. The pulling orretrieving may be performed periodically, continually, on demand, and/orin response to particular events (e.g., update of the information in theMSERV) but is not so limited. The information pulled by the MCS includesinformation of a “Global Address List” (“GAL”), information of one ormore “Public Folders,” “Personal Contacts,” and information of a “UserList.”

The GAL includes information of all users in the enterprise networkhaving access privileges that include the use of email. Public Foldersinclude information of the network enterprise (e.g., contacts,calendars, etc.) that are shared with all users. The Personal Contactsinclude contact information for each user.

The User List includes User Information for a subset of users in the GALeach of whom has access privileged that include the use of the ICS. TheUser List therefore is a subset of the GAL and is retrieved and/orcached as a separate list or stream in order to improve efficiency ofcommunications and minimize the delays associated with having the MCSsearch the entire contents of the GAL for information used in executinga user-requested action on a voice mail message. The User List of anembodiment includes one or more of the following parameterscorresponding to each user, but is not limited to these parameters: Siteidentification, mail box number, pronounceable name, office telephoneextension, COS, automatic attendant state (e.g., enabled, disabled),voice mail state (e.g., enabled, disabled); Voice User Interface (“VUI”)state (e.g., enabled, disabled), mobile access state (e.g., enabled,disabled), bad logins, locked out, attendant destination, force changeof PIN code, mobile gateway identification, full name, first name, lastname, user name, home telephone number, office telephone number,cellular telephone number, identification, email address, department,active greeting state, time and date announcement, voice mailnotification state (e.g., enabled, disabled), mail box status, PIN codein encrypted or raw form, no answer greeting, busy greeting, extendedabsence greeting, recorded name, and system greeting.

Instead of storing the information pulled from the MSERV in a separatevoice mail database as would be done in a typical voice mail system, thepulled information is pushed by the IM to the MCS and held in the Cache.The MCS uses the pulled information in subsequent voice mail messagemanipulation operations as described below. This pulling and caching ofinformation by the MCS improves the speed and efficiency of voice mailmessage operations and prevents unnecessary loads on the MSERV resultingfrom the nearly continuous stream of read requests to the MSERV databasein typical messaging systems.

The pulling of information from the MSERV by the MCS includes pullingand caching of information including the GAL, Public Folder, and UserList. The pulled information is cached by the MCS on a system ornon-individual basis because this information applies throughout theenterprise. This information is pulled and cached periodically, forexample at 24-hour intervals (e.g., each morning at 2:00 am), or may beloaded on demand, but is not so limited.

In contrast the MCS pulls and caches information of the PersonalContacts on a per user basis because this information is different foreach user. The Personal Contacts may be requested and cached by the MCSperiodically or on demand (e.g., at the time a user logs in to the ICS,in response to modifications of the Personal Contacts, etc.).

In operating to provide integrated messaging capabilities, the MCS andthe IM function to route a call placed by a caller to a user and, in theevent the user is not available, to receive and route a voice mailmessage left by the caller. The MCS and the IM also function to providea user with access to voice mail messages using the messaging server ofthe enterprise email system. The voice mail access supports both onlineand offline modes of the messaging server.

An example of call routing by the MCS, and with further reference toFIG. 6, the MCS receives and detects a call at the Telephony Interface.Data of the call (e.g., called party information, calling partyinformation, reason for call transfer, etc.) invokes the Voice Browser.The Voice Browser transfers a request to the Voice Applications inresponse to the call data.

A Dispatcher component of the Voice Applications routes the call to oneor more other Voice Application components in accordance withinformation of the User List. As an example, the Dispatcher identifiesthe target user for the call, and determines whether the target user'sautomatic attendant is enabled. If the automatic attendant is enabledthen the automatic attendant receives the call request and provides thecaller with one or more call routing options (e.g., caller selects callrouting by selecting and/or saying extension number, selecting and/orsaying name, etc.) and routes the call according to the caller's input.

As an example, one or more of the Voice Applications determine an activegreeting currently designated by the user for use in responding to calls(e.g., system greeting, no answer greeting, busy greeting, extendedabsence greeting, etc.), and retrieve the designated active greetingfrom one of the Cache or MSERV as appropriate to a state of the MSERV.The respective application(s) play the greeting, activate a “recordmode” to record the voice mail message of the caller, and provide thecaller with additional options available for call and/or message routing(e.g., message marking options, message delivery options, send message,route message to additional users, etc.). Upon completion of therecording and/or selection of a message routing option by the caller,the respective application(s) terminate the call (hangs up) and transferthe recorded voice mail message to one or more locations in the Cacheand/or MSERV (e.g., a mail box) that correspond to the user, asdescribed below with reference to FIGS. 8, 9, and 10. Alternatively, thevoice mail message may be transferred before the application terminatesthe call.

As referenced above, the MCS of an embodiment in conjunction with the IMsupports availability of and access to the voice mail applications whenthe MSERV is both “online” and “offline” through the use of the Cache.The MCS of an embodiment includes an “Offline Detector” that monitors anavailability state of the MSERV and detects unavailability (“offlinecondition” or “offline state”) of the MSERV. Upon detecting MSERVunavailability, the MCS transitions to a mode that supports voice mailmessage recording and retrieval during the MSERV offline condition.

Caching of select information received and/or generated in the MCS,including User Information and voice mail information, enhancesperformance of the enterprise network voice messaging system by reducingthe instances of data retrieval from the MSERV. Further, caching ofselect information improves the reliability of the enterprise networkvoice messaging system by allowing access to the voice messaging systemduring periods when the MSERV is offline.

Information received at the MCS is routed and held in the Cache inaccordance with policies running in the state machine framework and/orthe availability state of the MSERV. Examples of information held in theCache include but are not limited to the User List, Global Address List,information of Public Folders, information of Personal Contact Folders,voice mail message information (both the text description portion andthe audio message portion of the voice mail message), greetings, andother user parameters/permissions, and personal information of users(e.g., PIN codes).

Regarding actions taken by the MCS following receiving and recording ofa voice mail message when the MSERV is online, the MCS generally holdsinformation of the recorded message in the Cache. The MCS may alsotransfer the recorded voice mail message via the IM to the MSERV whereit is stored in the Database.

As an example, FIG. 8 is an information flow 800 for routing andaccessing voice mail messages via the ICS when the MSERV is in an onlinestate, under an embodiment. This information flow 800 shows one MCS andone MSERV in an enterprise network environment, but this is shown onlyas an example and does not limit the network environment to the types,numbers, and/or coupling of components shown as alternative embodimentsmay have any number of MCSs and/or MSERVs.

Information flow 800 begins when a caller places a call 802 to a userand availability of the user results in the caller leaving a voice mailmessage (referred to herein as the “VMSG”) for the user. The voice mailmessage VMSG is received at the MCS and routed 804C to the Cache whereit is assigned an identification (referred to herein as the “CACHEID”)and held. The voice mail message VMSG may be held in the Cache for apre-specified period of time, but the embodiment is not so limited. Thevoice mail message VMSG and the CACHEID are also routed 804M to theMSERV via the IM, as described above. The MSERV assigns anidentification (referred to herein as the “VMSGID”) to the incomingvoice mail message VMSG and stores 806 the voice mail message VMSG alongwith the VMSGID and CACHEID in one or more areas of memory (not shown)available to the MSERV. Memory may include any various form of storageor computer-readable memories such as, but not limited to, volatilememory (random access memory (“RAM”), non-volatile memory (read-onlymemory (“ROM”), EEPROM, disk, and/or other storage devices that mayinclude one or more of magnetic and optical storage media.

As described above, the MCS pulls information (e.g., periodically, ondemand, etc.) from the MSERV via the IM and uses the pulled informationin providing voice mail message capabilities integrated with emailmessaging capabilities of the enterprise network. Therefore, pullingoperations by the IM include pulling of information identifying thestored voice mail message VMSG, where the information identifying thevoice mail message VMSG includes but is not limited to the CACHEID. Uponrequest from the MCS, the IM may pull 808 a voice mail list (referred toherein as a “VMLIST” 809), which includes CACHEIDs and VMSGIDs for anystored messages from the MSERV environment. The IM pushes 810 VMLIST 809to the MCS where it is held. VMLIST 809 may be generated from the user'sinbox upon each request from the IM or may be stored and maintained inthe MSERV or in the cache as a current representation of the contents ofa user's voice mailbox, or inbox. If and when a time period for holdinga VMSG in the Cache expires, the VMSG is still identifiable from VMLIST809, and can be found in the MSERV if requested, using the VMSGID.

Information flow 800 continues when a user accesses 820 the enterprisenetwork system to retrieve his/her voice mail messages. In anembodiment, the user access 820 causes the VMLIST to be pulled 808 fromthe MSERV and pushed 810 by the IM to the Cache, and also oralternatively to the MCS Upon being provided with access to the MCS, theuser selects one or many voice mail message(s) by selecting aVMSGID/CACHEID item from the VMLIST. In response to the user selection,MCS searches 822 the Cache for a message, using the Cache identificationCACHEID of the selected message. In a scenario in which the message wasleft by the caller and the time period for holding the message VMSG inthe Cache has not expired, the MCS will locate the CACHEID and themessage contents VMSG in the Cache. Once located through use of theCACHEID, the MCS retrieves 814R the voice mail message contents VMSGfrom the Cache, and plays the voice mail message for the user asappropriate to the action selected by the user.

In this manner the MCS provides user access to the contents of the voicemail message VMSG via a mapping and without storing voice mail messagecontents in the MCS. The mapping includes a mapping of voice mailmessage contents to identification information of the email environment(MSERV environment), and mapping identification information of the emailenvironment to identification information of the voice mail environment(MCS). In this embodiment, therefore, the mapping includes mapping ofvoice mail message contents to the message identification VMSGID, andmapping of the message identification VMSGID of the email environment tothe MCS identification CACHEID.

As used herein “pushing” data or information indicates an action of acomponent or entity that has the affect of transferring the data orinformation to another component or entity. Transferring includessending in response to a request, query or command, and sending on theinitiative of the transferring component or entity. The transfer may bean internetwork transfer, an intranetwork transfer, or a transferbetween a network component or entity and a non-network component orentity.

As used herein “pulling” data or information indicates a component orentity receiving transferred data or information. Receiving includesreceiving in response to a request, query or command, and retrieving inresponse to a request, query or command. The transfer may be aninter-network transfer, an intra-network transfer, or a transfer betweena network component or entity and a non-network component or entity.

FIG. 9 is an alternative information flow 900 for routing and accessingvoice mail messages via the ICS when the MSERV is in an online state,under an embodiment. This alternative information flow 900 describes thescenario in which the message VMSG is left by the caller and stored inthe cache and in the MSERV environment, and after expiration of the timefor holding the message VMSG in the cache.

Information flow 900 begins when a caller places a call 802 to a userand availability of the user results in the caller leaving a voice mailmessage VMSG for the user. The voice mail message VMSG is received atthe MCS and routed 804C to the cache as described above, and the VMSGand CACHEID is routed 804 to the MSERV via the IM, also as describedabove. The MSERV assigns identification VMSGID to the incoming voicemail message VMSG and stores 806 the voice mail message VMSG along withthe VMSGID in one or more areas of memory (not shown) available to theMSERV.

Information flow 900 continues when a user accesses 820 the enterprisenetwork system to retrieve his/her voice mail messages. VMLIST 809 ispulled 808 from the MSERV and pushed 810 by the IM to the MCS. Uponbeing provided with access to the MCS, the user-selects a voice mailmessage from VMLIST 809, by selecting a CACHEID/VMSGID item. The MCSsearches 822 the Cache for the Cache identification CACHEID of theselected message in response to the user selection. Because the messagewas left by the caller and stored in the MSERV environment and expiredin the cache before the user calls in, the MCS will not locate theCACHEID in the Cache. Consequently, the MCS accesses the MSERV,identifies the message VMSG, and pulls 924R the voice mail messagecontents from the MSERV environment via the IM. The MCS plays the pulledvoice mail message VMSG for the user as appropriate to the actionselected by the user.

In addition to the online scenarios described above, the MCS of anembodiment provides offline behavior that allows for holding, storing,and retrieving voice mail messages when the MSERV is offline orunavailable for some reason, or during times when the connection betweenthe MCS and the MSERV is unreliable. Offline behavior means absence of acoupling between the MSERV and the MCS. Regarding actions taken by theMCS following recording of a voice mail message when the MSERV isoffline, a component of the MCS (e.g., Offline Detector) detects theMSERV is offline. The MCS holds the recorded voice mail message in thein response to detecting the MSERV state as offline. At such time as theMCS detects the MSERV is online, the Groupware Connector pulls the voicemail message from the Cache and transfers the recorded voice mailmessage via the IM to the MSERV where it is stored in the Database.

As an example, FIG. 10 is an information flow 1000 for routing andaccessing voice mail messages via the ICS when the MSERV is in anoffline state, under an embodiment. This information flow 1000 shows oneMCS and one MSERV in an enterprise network environment, but this isshown only as an example and does not limit the network environment tothese components as alternative embodiments may have any number of MCSsand/or MSERVs.

The information flow 1000 begins when a caller places a call 802 to auser and availability of the user results in the caller leaving a voicemail message VMSG for the user. The voice mail message VMSG is receivedat the MCS, however a component of the MCS detects an unavailable oroffline condition of the MSERV. In response to detecting the offlinecondition, the MCS assigns a CACHEID to the incoming message VMSG, andholds 1004C the message contents VMSG along with the CACHEID in theCache.

Information flow 1000 continues when a user accesses 820 the enterprisenetwork system to retrieve his/her voice mail messages while the MSERVremains in an offline condition. Upon being provided with access to theMCS, the user selects a voice mail message from a list of CACHEIDsgenerated from the collection of voice mail messages held for him/her inthe cache. In response to the user selection, the MCS searches 1022 theCache using the Cache identification CACHEID of the selected message.Upon locating the voice mail message by its CACHEID in the Cache, theMCS pulls 1014R the voice mail message contents from the Cache, andplays the voice mail message for the user as appropriate to the actionselected by the user.

The MCS continues to monitor the condition of the MSERV. At such time asthe MCS detects a return of the MSERV to an online condition, the MCSpulls 1004P the voice mail message VMSG and its CACHEID from the Cache,and transfers 1004M the voice mail message and CACHEID via the IM to theMSERV. The MSERV assigns an identification VMSGID to the incoming voicemail message VMSG and stores 1006 the voice mail message VMSG along withthe VMSGID and CACHEID in one or more areas of memory as describedabove.

In addition to the capabilities described above, the ICS of anembodiment provides a Form-Based User Interface (“FBUI”). The FBUI is aform-based messaging or communication interface for use by users inretrieving voice mail messages and controlling actions taken on voicemail messages received in the enterprise network system. This FBUIenables a user to retrieve and take various actions on voice mailmessages using data of a form (referred to herein as the “FBUI FORM”)that is presented to the user's client device by the enterprise networkemail system. Use of the FBUI Form thus provides the user with access tothe integrated messaging functions offered by the ICS without arequirement to install or run a dedicated client application on theuser's client device.

FIG. 11 is a block diagram of a system 11 that includes ICS 1100 withFBUI 1180, under an embodiment. System 11 includes an enterprise network1101 that provides integrated voice mail and email messaging through theuse of ICS 1100. Enterprise network 1101 includes a LAN that couples tocomponents of ICS 1100 and a messaging server environment 1140. ICS 1100includes MCS 1110 IM 1120, and FBUI 1180, but is not so limited. FBUI1180 is presented to a user (e.g., USER Z) via one or more local deviceslike PCs or other processor-based devices.

Messaging server environment 1140 includes the MSERV and a Database1144, but is not so limited. The LAN couples to any number of othernetworks 1150 and 1160 using any of a variety of communicationprotocols, where the networks 1150 and 1160 may be of the same or ofdifferent types. As an example, the networks may include a publiccommunications network 1150 and a private communications network 1160.Private communications network 1160 may be a PBX coupled to the LAN ofthe enterprise network, for example. Networks 1150 and 1160 allow forinformation transfers between client devices 1170 that are local toenterprise network 1101 and client devices 1199 that are external toenterprise network 1101. The client devices may alternatively bereferred to as “user devices” 1170 and 1199.

ICS 1100 replaces the voice mail server typically found in enterprisenetworks with at least one MCS 1110. MCS 1110 is coupled to the privatecommunications network (e.g., PBX) of each network enterprise. While oneMCS is shown in this example system 11, the enterprise network mayinclude multiple MCSs 1110 coupled to enterprise network in an “N+1”configuration, where “N” is any number 1, 2 . . . X.

For security reasons, communication to and from the MCS is restricted inan embodiment. The MCS communicates with the IM servers, the privatecommunications network, other MCSs and selected client devices.According to an embodiment of the invention, communications with the MCSmay be restricted to network components having particular knownaddresses. Additionally or alternatively, communications with the MCSmay require authentication by passcode or other security measures forcertain kinds of access, for example, for access by the administrator.Security may also or alternatively be encrypted and/or provided byrequiring a physical connection between the MCS and other component,such as in the case of a connection between an MCS and a privatecommunications network through a direct cable connection.

The MCS via the FBUI generally provides a form to a client device from afirst server (e.g., messaging server, MSERV, etc.) via a networkconnection. The form includes data or code that when executed by thereceiving client device results in presentation of a FBUI on a displayof the client device. The FBUI includes a number of buttons or iconsthat allow a user to select an action on an item via a second server(e.g., communication server, MCS, etc.), where the item is stored on thefirst and/or second servers, and the first and second servers aredifferent servers. The FBUI of an embodiment uses a web browser embeddedin the form as the means for coupling and/or communicating with acorresponding browser control of the second server. Communicationsbetween the client device and the second server thus avoid securityand/or other network policy issues that would prohibit the client devicefrom communicating with the second server via the network couplingbetween the client device and the first server.

As described above, the FBUI operates as a form-based messaginginterface to transfer a first message (e.g., voice mail message) to amessaging server (e.g., MSERV) from a communication server (e.g., MCS)via a first coupling (e.g., IM). The messaging server generates a secondmessage (e.g., email message) in response to a type of the first messageand transfers the second message to a client device via a secondcoupling (e.g., LAN). The type of the first message is specified by thecommunication server using properties on the message that identify themessage as a “Voice Mail Type” (“VMT”) message. The second message is ofa different type and includes data of the first message, but is not solimited. The communication server also transfers to the client deviceform data that corresponds to the first message. The client device usesthe form data to establish a third coupling (e.g., browser link) betweenthe client device and the communication server. The user may directactions on the first message from the client device via the thirdcoupling using the form data.

The ICS of an embodiment provides the FBUI 1180 to a user via his/herlocal client device. The FBUI is provided to the client device throughthe use of a FBUI Form, where the structure of the FBUI Form conforms tothe message structure of the messaging server environment. For example,when the messaging server environment includes the use of MicrosoftExchange and Microsoft Outlook, the FBUI Form is generated to complywith Microsoft formats as appropriate to Exchange and Outlook

Information for generation of the FBUI Form is provided to the messagingserver environment by the MCS via the IM, and the code used for FBUIForm generation is hosted by the MSERV in an embodiment. The FBUI Formof an embodiment includes code that generates information of the FBUIdisplay as well as the buttons of the display. The FBUI Form furtherincludes an embedded browser control for use in establishingcommunications between the client device displaying the FBUI Form and aweb server (e.g., MCS, IM, other server) for example. The embeddedbrowser control therefore allows the host client device to couple andcommunicate with a server that is different from the MSERV via acommunication channel that is outside the enterprise network LAN. Thus,the FBUI Form enables a communication channel between the local clientdevice currently executing the form and a component like the MCS and/orIM in spite of network policy issues that otherwise might prohibit theclient device from communicating outside the enterprise network messageinfrastructure.

Using the FBUI, a user can access/view and take a variety of actions onhis/her voice mail messages within an email framework of the hostenterprise network system. As an example, when the MCS of an embodimentreceives a voice mail message it transfers the voice mail message to theMSERV, as described above. In transferring the voice mail message to theMSERV, the MCS specifies properties on the message that identify themessage as a “Voice Mail Type” (“VMT”) message. The message is receivedand stored by the MSERV as a VMT message using the same storage andretrieval structure as used with other message types like emailmessages.

At such time as a user wishes to access his/her messages via his/herclient device, the active message browser of the client device receivesthe VMT message along with any other mail messages currently stored inhis/her electronic mail box. The message browser corresponds to themessage structure of the messaging server environment (e.g., Outlook ina Microsoft environment). Upon receipt of the message, the messagebrowser identifies the message as a VMT message. As the code thatimplements the FBUI Form is stored on the MSERV, implementation of thefunctionality and/or features associated with the FBUI Form usescommunication between the user's client device and the MSERV via theLAN. For example, the client device message browser requests the FBUIForm from the MSERV in response to identifying a message as a VMTmessage because this is the form that corresponds to the VMT messagetype. The MSERV transfers the FBUI Form to the requesting client device,and the client device message browser launches the form in response tothe user selecting a VMT message for viewing.

The message browser uses data or code of the FBUI Form to display theFBUI on the user's client device. FIG. 12 is a sample FBUI 1200 asdisplayed on a client device, under an embodiment. The FBUI 1200includes three areas 1202-1206 that present information to a user. Theareas include a folder area 1202, a contents area 1204, and a functionarea 1206, but are not limited to these areas as the UIs of alternativeembodiments may present any number and/or type of areas. In alternativeembodiments, all three areas 1202-1206 may be presented at the sametime, as shown in FBUI 1200, or various subsets of the three areas maybe presented at the same time in various combinations.

Folder area 1202 presents one or more folders to which the user hasaccess via the FBUI 1200 and the client device. The “INBOX” may containa list of voice mail messages in the same listing as other messages,including email messages. Alternatively, the Inbox may include asubfolder (“VOICE MESSAGES”) which includes the voice mail messages, andselection of this folder results in the presentation of voice mailmessages of the user's mail box in the contents area 1204.

The contents area 1204 generally presents the contents of the folderselected using the folder area 1202. As an example, the contents area1204 presents information corresponding to any number of voice mailmessages in the user's mail box when the INBOX or VOICE MESSAGES folderis selected. Contents area 1204 allows the user to select a particularvoice mail message by placing a cursor on “VOICE MESSAGE 1 INFORMATION”for example. By (double) clicking a message in the contents area 1204 orotherwise indicating to the message browser to display a voice message,a new window (referred to as the “ICS Window”) is displayed. The ICSWindow now includes function are 1206.

Function area 1206 of FBUI 1200 presents one or more “voice mail actionbuttons” 1206A-1206E (also referred to herein as “buttons”) each ofwhich represents an action the user may select for a voice mail message.In this example, the VOICE MESSAGES folder is selected, and selection ofa message in contents area 1204 allows the user to take an action on theselected message using buttons 1206A-1206E. Placing the cursor ofcontents area 1204 on a particular message and choosing an action on theselected message with a button 1206A-1206E therefore invokes operationson the message via components of the ICS (e.g., MCS, Cache, IM). Thebuttons 1206A-1206E of an embodiment include a “Play on Phone” button1206A, a “Play on Computer” button 1206B, a “Call Sender” button 1206C,a “Reply by Voicemail” button 1206D, and a “Forward by Voicemail” button1206E, but the embodiment is not limited to this same number of buttonsor to buttons offering the same functionality.

In other embodiments, presentation of areas or information of the FBUImay vary in many ways. For example, in one embodiment, the actionbuttons 1206 appear after the user has selected (for example by doubleclicking a particular voice message from the contents area 1204. Actionbuttons 1206 may also appear when the user right clicks on a particularvoice message in the contents area 1204.

The folder area 1202 may also include a subfolder (“VOICE MESSAGESYSTEM”) under the Public Folder. As such, the VOICE MESSAGE SYSTEMfolder may not be considered an actual folder but instead a uniformresource locator (“URL”) that, when selected, sends an HTTP request to aweb server and launches/displays an ICS browser inside the client devicemessage browser. The web server may, for example, be a component of theMCS and/or IM, but is not so limited. The ICS browser is an embedded orhidden browser that displays the ICS Window in the area of the clientdevice message browser where emails would typically appear, and thevoice mail messages are displayed in the ICS Window.

As an example, the ICS Window is displayed in the contents area 1204 ofan embodiment. The ICS Window may be served from the IM and may containany information related to the voice messaging system that is userspecific. In one embodiment, the ICS Window will display a user loginprompt where the user enters the user name and PIN code. Subsequently,the system displays the user's configuration date, such as PIN code,attendant extension, greeting type, and other applicable information.

The hidden browser enables an HTTP link and communications with the IM,for example, which then brokers communications (via HTTP) with the MCSvia the MCS Web Server (FIG. 6) for example. Therefore, while typicalmessaging servers and LANs use security policies that restrict the useof “special” code in form data, use of the hidden browser embedded in aform structure that is native to the host system overcomes thisrestriction because the browser is not detected or considered as specialcode. Use of the hidden browser thus supports communication with thecorresponding browser control in the MCS and/or the IM, thereby allowingthe integration of voice mail messaging provided by the MCS with theemail messaging system of the enterprise network

A “voice mail message” in the ICS is generally any message created usinga client device generating an audio stream. A “voice mail message” isalso any VMT message, such as a message created using the “Reply byVoice Message” and “Forward by Voice Message” buttons of the FBUI. An“email” is any message created using buttons of a host mail messagesystem that function to generate a reply message or to forward a messagein response to receipt of a message, even if replying or forwarding avoice mail message. The ICS of an embodiment presents a voice mailmessage to a user in an email message system using the FBUI as thepresentation form.

As described above, FBUI 1200 allows a user to take action on a voicemail message via buttons 1206A-1206E of FBUI 1200. Therefore, placingthe cursor of contents area 1204 on a particular message and choosing anaction on the selected message with a button 1206A-1206E invokes theaction on the message via components of the MCS and/or the enterprisenetwork environment.

As one example of an action on a voice mail message, and with furtherreference to FIG. 11, the user may select a “Play on Phone” action usingbutton 1206A. In response the user's client device couples to acomponent of the ICS (e.g., IM) using the hidden browser of the FBUI.The client device receives a pop-up message from the ICS via the browserlink and the ICS Window, where the pop-up message allows the user tochoose or enter a telephone number to which he/she would like theselected voice mail message routed. The pop-up message also includes a“connect” button by which the user initiates routing of the selectedvoice mail message to the selected telephone. In response to selectionof the “connect” button, the IM couples with an MCS, and the MCS causesthe PBX to initiate a call to the telephone number selected by the uservia the pop-up window. Upon connection of the call from the PBX to theselected telephone, the MCS pushes the contents of the voice mailmessage to the selected telephone.

Another example of an action on a voice mail message includes selectionof a “Play on Computer” action by the user via button 1206B. In responsethe user's client device couples to a component of the ICS (e.g., IM)using the hidden browser of the FBUI. In response to selection of the“Play on Computer” button, the IM couples with an MCS, and the MCSpushes a form to the user's computer that resembles a typical email. Theform includes an attachment that is an audio file (e.g., WAVE, MP3,other audio formats, etc.). When the user selects the attachment theclient device may launch the default audio player of the client device.

Alternatively, selection of the attachment in a “Play on Computer”action may result in the browser form controlling launch of apre-specified audio player instead of the default audio player. This issimilar to the hidden browser described above with reference topresentation of the FBUI.

The user may also select a “Call Sender” action on a voice mail messageusing button 1206C. In response the user's client device couples to acomponent of the ICS (e.g., IM) using the hidden browser of the FBUI. Inresponse to selection of the “Call Sender” button, the IM couples withan MCS, and the MCS retrieves the selected message from the Cache or theMSERV. Using the caller information from the retrieved message, the MCScauses the PBX to connect the call to the user's local telephone. Uponconnection of the call from the PBX to the user's telephone, the MCScauses the PBX to initiate a call to the sender's telephone number asdetermined from the caller information associated with the voicemessage.

Additionally, the user may select a “Reply by Voice Message” action on avoice mail message using button 1206D. In response the user's clientdevice couples to a component of the ICS (e.g., IM) using the hiddenbrowser of the FBUI. In response to selection of the “Reply by VoiceMessage” button, the IM couples with an MCS, and the MCS retrieves theselected message from the Cache or the MSERV. The MCS causes a replymessage to be generated corresponding to the received message, andprompts the user to record an audio message for the reply. The userrecords the audio for the reply via a microphone coupled to his/herclient device. Alternatively, the user may record the audio for thereply via his/her local telephone. Upon completing the audio replyrecording, the MCS causes the reply message to be transmitted to thedesignated addressees via the MSERV. A user is not required to listen toa message to invoke the “Reply by Voice Message” action.

The user may also select a “Forward by Voice Message” action on a voicemail message using button 1206E. In response the user's client devicecouples to a component of the ICS (e.g., IM) using the hidden browser ofthe FBUI. The client device receives a pop-up message from the ICS viathe browser link, where the pop-up message allows the user to choose orenter a telephone number to which he/she would like the selected voicemail message routed. The pop-up message also includes a “connect” buttonby which the user initiates routing of the selected voice mail messageto the selected telephone. In response to selection of the “connect”button, the IM couples with an MCS, and the MCS causes the PBX toinitiate a call to the telephone number selected by the user via thepop-up window. Upon connection of the call from the PBX to the calledtelephone selected by the user, the MCS pushes the contents of the voicemail message to the called telephone and the user. During the session,and in addition to the contents of the voice mail message, the MCS mayprovide a verbal prompt to the user requesting information of the partyto whom the message is to be forwarded, and/or a prompt to the user torecord an audio message to be forwarded along with the forwardedmessage. A user is not required to listen to a message to invoke the“Forward by Voice Message” action.

More generally, FIG. 13 is a block diagram of a system 1300 that uses aform-based interface 1380 transferred in a first type of message forcontrolling actions on a second type of message, along with thecorresponding information flows, under an embodiment. System 1300generally includes an enterprise network 1301 coupled to one or morepublic communications networks 1350 via a private communication network1360. Enterprise network 1301 includes at least one first server(“Server A”) and at least one interface module 1320, both of whichcouple to a LAN. Server A also couples to private communication network1360. In an embodiment, components of Server A and interface module 1320function collectively to form an ICS, as described herein, but are notlimited to ICS functionality.

System 1300 further includes a backend network environment 1340 and auser workstation 1370, each of which couple to the LAN. Backend networkenvironment 1340 includes at least one server (“Server B”) but mayinclude any number of servers, databases, and/or other components.Components of user workstation 1370 also couple to the LAN, theworkstation components including a telephone 1370P and a client device1370C that are local to enterprise network 1301. Server A and interfacemodule 1320 cause form-based interface 1380 to be displayed to User Zvia Server B and client device 1370C. Public communications network 1350and enterprise network 1301 allow information transfers betweencomponents that are local to enterprise network 1301 and client devices1399 that are external to enterprise network 1301.

In response to receiving a data stream at an input of privatecommunication network 1360, enterprise network 1301 uses the integratedcommunication processes described herein to cause Server A to generateand transfer a first message to Server B. The first message istransferred to Server B via interface module 1320. Server B generates asecond message in response to properties of the first message, andtransfers the second message to local client device 1370C via the LAN.The second message is a different type message than the first messageand includes information of the first message. In an embodiment, a typeof the first message is a voice mail type, and a type of the secondmessage is an email type.

Local client device 1370C requests form data from Server B in responseto information of the first message, and Server B in turn provides therequested form data to local client device 1370C via the LAN. Localclient device 1370C executes the form data resulting in presentation ofform-based interface 1380 on a display of user workstation 1370.

While local client device 1370C is described as being local toenterprise network 1301, it is understood that client device 1370C isnot required to reside at any particular physical location withinenterprise network 1301. For example, “local” client device 1370C may bea tablet PC 1370C from which User Z (who is off site) remotely accessescomponents of enterprise network 1301 (e.g., Server B) via a virtualprivate network (“VPN”) for example.

Upon display on local client device 1370C form-based interface 1380presents a number of soft buttons 1306 or action buttons 1306 that allowUser Z to control actions on data that resides at Server A and/or ServerB via communications with interface module 1320 and Server A. Theseactions are controlled via a form browser control embedded in the formdata. This form browser control thus allows the local client device (viathe form-based interface) to couple to and communicate with Server A viaan “Independent Access Channel” (“IAC”) (e.g., browser link) that isindependent of the LAN. The coupling between local client device 1370Cand Server A is via a corresponding browser control of Server A andinterface module 1320 but is not so limited.

Action buttons 1306 of form-based interface 1380 enable User Z tocontrol or direct actions on data held and/or stored at Server A and/orServer B. The data may be the first message that was previouslytransferred to Server B, but is not so limited; this first message maybe held at Server A and/or stored at Server B as appropriate to a state(e.g., online, offline) of Server B, as described above. Action buttons1306 of form-based interface 1380 enable user control of actions on thedata held and/or stored at Server A and/or Server B via the IAC betweenlocal client device 1370C, interface module 1320, and Server A.

Each of action buttons 1306, when selected by User Z, calls the formdata of the form-based interface form as appropriate to the actioncorresponding to the selected action button 1306. The form data locatesthe browser control corresponding to the action selected by User Z, andthe browser control directs the embedded browser of the form-basedinterface form to the corresponding URL of interface module 1320 and/orServer A. As such, selection of an action button establishes the IACbetween local client device 1370C, interface module 1320, and Server A.

In response to selection of one or more actions via the action buttons,Server A may transfer status and/or control data (referred to as“status/control data”) to local client device 1370C via the establishedIAC. Server A of an embodiment transfers the status/control data viainterface module 1320, but is not so limited. Execution of thestatus/control data on local client device 1370C results in the displayof popup 1382, where popup 1382 is a web browser window that may besmaller than form-based interface window 1380 and without some of thestandard features such as tool bars.

Popup 1382 may present User Z with information regarding status of theselected action, prompts to select information via popup 1382, promptsto enter information via one or more fields of popup 1382, and promptsto initiate further actions, but is not limited to presentation of onlythis information. In response to entry of any additional informationinto popup 1382 in response to queries or prompts and/or selection ofany further actions by User Z, local client device 1370C transfers dataof the additional information and/or selection to Server A via theestablished IAC and interface module 1320.

In an example in which server actions are controlled via a form-basedinterface, with continued reference to FIG. 13, Server A generates andtransfers a first message to Server B via interface module 1320. ServerB in turn generates a second message in response to properties of thefirst message, and transfers the second message to local client device1370C via the LAN. Local client device 1370C requests and receives viathe LAN form data from Server B in response to information of the firstmessage. Local client device 1370C executes the form data and presentsform-based interface 1380 on a display of local client device 1370C.

Form-based interface 1380, as described above, presents one or more softaction buttons 1306 to User Z. Selection of an action button 1306 byUser Z establishes communication 1306-1 between local client device1370C and Server A via the IAC and interface module 1320. Server Adetermines a location of information needed to fulfill the requestedaction. If Server A determines the action corresponding to selectedaction button 1306 uses information from backend network environment1340 (e.g., Server B), then Server A directs 1306-2 interface module1320 to pull 1306-2 the information from components of the backendnetwork environment as described above, and interface module 1320 pushes1306-2 the pulled information to Server A.

Server A executes the action on the information as appropriate toselected action button 1306. As an example, the action may includeestablishing communication with 1306-3A and/or forwarding theinformation to an external client device 1399. Establishingcommunication 1306-3A and/or forwarding takes place via a couplingbetween Server A and external client device 1399 that includes one ormore of private communication network 1360 and public communicationsnetwork 1350, but is not so limited.

As another example, the selected action may include establishingcommunication with 1306-3B and/or forwarding the information to a clientdevice 1370 within enterprise network 1301. The client device ofenterprise network 1301 includes a local user telephone 1370P or clientdevice 1370C, for example, but can include a variety of devices.Establishing communication 1306-3B and/or forwarding takes place via acoupling between Server A and local client device 1370P/1370C thatincludes one or more couplings via the LAN, but is not necessarily solimited.

In response to selection of one or more actions via the action buttons,Server A may transfer 1310-SC status/control data to local client device1370C via the established IAC. Server A of an embodiment transfers1310-SC the status/control data via interface module 1320, but is not solimited. Execution of the status/control data on local client device1370C results in the display of a popup 1382 on a display of localclient device 1370C via the form-based interface. Popup 1382 presentsthe status/control data to User Z. In response to entry of anyadditional information into popup 1382 in response to queries or promptsand/or selection of any further actions by User Z, local client device1370C transfers 1306-1 data of the additional information and/orselection to Server A via the established IAC and interface module 1320.

As generally described above, the form-based interface of an embodimentmore specifically includes the FBUI of the ICS. The FBUI operates as aform-based messaging interface to transfer a first message (e.g., voicemail message) to a messaging server (e.g., MSERV) from a communicationserver (e.g., MCS) via a first coupling (e.g., IM). The messaging servergenerates a second message (e.g., email message) in response to a typeof the first message and transfers the second message to a client devicevia a second coupling (e.g., LAN). The type of the first message isspecified by the communication server using properties on the messagethat identify the message as a “Voice Mail Type” (“VMT”) message. Thesecond message is of a different type and includes data of the firstmessage, but is not so limited. The communication server also transfersto the client device form data that includes the FBUI Form, where theFBUI Form corresponds to the first message. The client device uses theFBUI Form data to establish a third coupling (e.g., browser link)between the client device and the communication server. The user maydirect actions on the first message from the client device via the thirdcoupling using the form data.

Referring again to FIGS. 12 and 13, the ICS of an embodiment providesthe FBUI to a user via his/her local client device. The FBUI is providedto the client device through the use of a FBUI Form, where the structureof the FBUI Form conforms to the message structure of the messagingserver environment. For example, when the messaging server environmentincludes the use of Microsoft Exchange and Microsoft Outlook, the FBUIForm is generated to comply with Microsoft formats as appropriate toExchange and Outlook.

Information for generation of the FBUI Form is provided to the messagingserver environment by the MCS via the IM, and the code used for FBUIForm generation is hosted by the MSERV in an embodiment. The FBUI Formof an embodiment includes code that generates information of the FBUIdisplay as well as the buttons of the display. The FBUI Form furtherincludes an embedded browser control for use in establishingcommunications between the client device displaying the FBUI Form and aweb server (e.g., MCS, IM, other server) for example. The embeddedbrowser control therefore allows the host client device to couple andcommunicate with a server that is different from the MSERV via acommunication channel IAC that is outside the enterprise network LAN.Thus, the FBUI Form enables a communication channel between the localclient device currently executing the form and a component like the MCSand/or IM in spite of network policy issues that otherwise prohibit theclient device from communicating outside the enterprise network messageinfrastructure.

The FBUI thus allows a user to access, view and take a variety ofactions on his/her voice mail messages within an email framework of thehost enterprise network system. As an example, when the MCS of anembodiment receives a voice mail message it transfers the voice mailmessage to the MSERV, as described above. In transferring the voice mailmessage to the MSERV, the MCS specifies properties on the message thatidentify the message as a VMT message. The message is received andstored by the MSERV as a VMT message using the same storage andretrieval structure as used with other message types like emailmessages.

At such time as a user wishes to access his/her messages via his/herclient device, the active message browser of the client device receivesthe VMT message along with any other mail messages currently stored inhis/her electronic mail box. The message browser corresponds to themessage structure of the messaging server environment (e.g., Outlook ina Microsoft environment). Upon receipt of the message, the messagebrowser identifies the message as a VMT message. As the code thatimplements the FBUI Form is stored on the MSERV, implementation of thefunctionality and/or features associated with the FBUI Form usescommunication between the user's client device and the MSERV via theLAN. For example, the client device message browser requests the FBUIForm from the MSERV in response to identifying a message as a VMTmessage because this is the form that corresponds to the VMT messagetype. The MSERV transfers the FBUI Form to the requesting client deviceas client-side code, and the client device message browser launches theform in response to the user selecting a VMT message for viewing.

As one example of an action on a voice mail message, and with furtherreference to FIG. 12, the user may select a “Play on Phone” action usingbutton 1206A. In response the user's client device couples to acomponent of the ICS (e.g., IM) using the hidden browser of the FBUI.The client device receives a popup message from the ICS via the browserlink, where the popup message allows the user to choose or enter atelephone number to which he/she would like the selected voice mailmessage routed (the MCS may not display the popup window if, during anactive Play on Phone session, a user selects a second voice mail messagefor play). The popup message also includes a “connect” button by whichthe user initiates routing of the selected voice mail message to theselected telephone. In response to selection of the “connect” button,the IM couples with an MCS, and the MCS causes the PBX to initiate acall to the telephone number selected by the user via the popup window.Upon connection of the call from the PBX to the selected telephone, theMCS pushes the contents of the voice mail message to the selectedtelephone.

In response to selection of one or more actions via the action buttons,ICS components of an embodiment may transfer status/control data inresponse to actions selected via the action buttons. As described abovewith reference to FIG. 13, execution of the status/control data on thelocal client device results in the display of a popup window. The popupis a web browser window that may present a user with information thatincludes prompts to select information needed by the ICS to complete anaction, prompts to enter information needed by the ICS to complete anaction, status of a selected action, and prompts to initiate furtheractions, but is not limited to presentation of only this information.

As an example, FIG. 14 is a selection popup 1400, or ICS Window the ICSprovides during execution of the Play on Phone action, under anembodiment. The ICS presents selection popup 1400 as a means by which auser selects or enters information needed by the ICS to complete anaction corresponding to a selected action button. Selection popup 1400of this example (“Voice Message Interface Call Number”) allows the userto choose a telephone number (e.g., “Work Phone” 1402, “Cell Phone”1404, “Home Phone” 1406) to which he/she would like the selected voicemail message routed. Selection popup 1400 also allows the user to enterinto a popup field 1408 a telephone number to which he/she would likethe selected voice mail message routed. Popup message 1400 also includesa “Call” button 1410 by which the user initiates connection and/orrouting of the selected voice mail message to the selected telephone.Selection/entry of a telephone number and activation of “Call” button1410 by the user causes the local client device to transfer theselection/entry to the ICS.

As another example, FIG. 15 is a status popup 1500 the ICS providesduring execution of the Play on Phone action, under an embodiment. TheICS presents status popup 1500 to provide the user with statusinformation of the selected action (e.g., “Play on Phone”). Status popup1500 of this example (“Voice Message Call Status”) informs the user thatcurrent status 1502 of the call to the number previouslyselected/entered (FIG. 14) is “Connecting”, but the status may includeother status information including but not limited to “dialing”, “linebusy”, “unable to complete call”, “no answer”, etc. Any amount or typeof status information may be displayed using any number and/orcombination of popup windows in alternative embodiments.

FIG. 16 is another status popup 1600 the ICS provides during executionof the Play on Phone action, under an embodiment. The ICS presentsstatus popup 1600 to provide the user with status information of theselected action (e.g., “Play on Phone”). Status popup 1600 of thisexample (“Voice Message Call Status”) informs the user that currentstatus 1602 of the call to the number previously selected/entered (FIG.14) is “Line Busy”. Status popup 1600 also includes a “Close” button1602 by which a user terminates presentation of popup 1600.

Components of the ICS of an embodiment provide for storage of voice mailmessages in an email messaging structure of an enterprise network asdescribed above. The ICS components also provide a form-based interfaceto a client device via the messaging server. The ICS and form-basedinterface also provide the user with a system for accessing anddirecting action on the voice mail messages outside of the communicationpolicies of the enterprise network. The form-based interface alsoeliminates the requirement for a dedicated client application on theuser's client device.

One action the ICS allows on voice mail messages is the Play on Phoneaction described above. Play on Phone allows a user accessing theenterprise network via a local client device to select a telephone towhich voice mail messages can be forwarded. As an example, a user who isaway from the office on vacation may access the enterprise network usinga portable computer (e.g., via VPN) and use the Play on Phone action ofthe FBUI to direct his/her voice mail messages to be routed to his/hercellular telephone. In response, components of the enterprise networkincluding the ICS initiate a call to the user's cellular telephonenumber, retrieve the selected voice mail messages, and play the messagesover the call.

The operation of routing voice mail messages to a user-selected devicelike a telephone during the Play on Phone action includes a number ofinformation transfers among components of the ICS and the hostenterprise network. FIG. 17 is an information flow in a system 1700 thatincludes an ICS supporting Play on Phone operations, under anembodiment. System 1700 includes an enterprise network 1701 coupled toone or more public communications networks 1750 via a PBX. Enterprisenetwork 1701 includes at least one MCS and at least one IM, both ofwhich couple between the PBX and a messaging and collaboration serverMSERV. In an embodiment, components of the MCS and IM functioncollectively to form the ICS, as described herein, but operation of theMCS and/or IM is not limited to ICS functionality. System 1200 furtherincludes at least one local client device 1770 that couples toenterprise network 1701.

The MCS and IM operate to cause FBUI 1780 to be displayed to User Z viathe MSERV and local client device 1770. Public communications network1750 and enterprise network 1701 allow information transfers betweenclient devices 1770 that are local to enterprise network 1701 and clientdevices 1799 that are external to enterprise network 1701. In thisexample external client device 1799 is a cellular telephone of User Z,but is not so limited.

The information flow begins when the PBX transfers 1702 a data stream tothe MCS. The data stream may for example be an audio stream of anincoming call from a caller to User Z. Enterprise network 1701 usesprocesses of the ICS described herein to cause the MCS to generate andtransfer 1703 a first message to the IM. The first message includesinformation of the received data stream, and a type of the first messageis a voice mail message, but is not so limited. The IM in turn transfers1704 the first message to the MSERV. The MSERV generates a secondmessage in response to properties of the first message, and transfers1705 the second message to local client device 1770 via communicationsover the enterprise network. The type of the second message is an emailmessage, where the email message includes information of the firstmessage, but is not so limited.

Local client device 1770 receives the second message and requests 1706form data from the MSERV in response to information of the secondmessage. The MSERV retrieves 1707 the requested form data, and transfers1708 the retrieved form data to local client device 1770 via theenterprise network. Local client device 1770 executes the form dataresulting in presentation of FBUI 1780 on a display of user workstation1770.

While local client device 1770 is described as being local to enterprisenetwork 1701, it is understood that client device 1770 is not requiredto reside at any particular physical location within enterprise network1701. For example, “local” client device 1770 may be a portable PC 1770from which User Z (off site) remotely accesses components of enterprisenetwork 1701 (e.g., MSERV) via a VPN.

FBUI 1780, as described above, presents one or more soft action buttons1782 to User Z. This example assumes selection of Play on Phone button1782 by User Z. Selection of Play on Phone establishes communication1710 between local client device 1770 and the MCS via the IAC and theIM.

As an example of establishing communication 1710, selecting Play onPhone via the FBUI causes the client device local browser to call thefunction in the form data that corresponds to the Play on Phoneoperation. The form data when called generates a URL request (code)corresponding to the Play on Phone action, and the URL request expressesthe ICS data that is to be transferred to the IM and the MCS. The ICSdata of the URL request includes for example a message identificationcorresponding to the selected voice mail message (for use by the IM/MCSin accessing the voice mail message stored in the MSERV environment),user identification, and identification information of the actiondesired by User Z (Play on Phone). The URL request subsequently directsthe FBUI embedded browser to the specified URL.

In response to receiving the URL request via communication 1710 fromlocal client device 1770, the MCS determines a location of information(e.g., user information, voice mail message contents, etc.) needed tofulfill the Play on Phone operation. If the MCS determines the Play onPhone uses information from the MSERV environment, then the MCS directs1703 the IM to pull 1712 the information from components of the MSERVenvironment as described above (e.g., directory service), and the IMreturns 1703 the pulled information to the MCS.

In response to selection of Play on Phone, the MCS generates andtransfers 1714 status/control data (e.g., HTML) to local client device1770 via the IAC. Execution of the status/control data on local clientdevice 1770 causes the FBUI embedded browser to display a popup window1784.

Popup window 1784 corresponding to status/control data transfer 1714 forexample is selection popup 1400 described with reference to FIG. 14.This example assumes User Z directs 1716 routing of his/her voice mailmessages to his/her cellular telephone 1799 by selecting “Cell Phone” inpopup 1784, but the embodiment is not so limited. The selection of “CellPhone” along with activation of the “Call” button via popup 1784 causesthe form data to generate another URL request (code) that is transferred1716 to the IM and the MCS.

Upon receiving the URL request with the selected cellular telephonenumber from local client device 1770, the IM uses the messageidentification of the selected voice mail message, user identification,and the selected cellular telephone number to transfer a request to theMCS for initiation of the Play on Phone call.

The MCS initiates a call to cellular telephone 1799 via communications1702 with the PBX. The MCS, which manages call functions of the ICS,initiates the call by directing the PBX to place the call to cellulartelephone 1799. The MCS enforces any User Z COS parameters of enterprisenetwork 1701. The call is made via any number of telephony interfacesincluding T1/E1, DSE, VoIP, and analog, but is not so limited.

During the process of initiating 1702 the call, the MCS transfers 1718status information of the call (e.g., from the PBX) to local clientdevice 1770. The MCS transfers 1718 via the IM the status informationusing a status message in popup window 1784 to provide the user withstatus information of the Play on Phone call to his/her cellulartelephone. An example of status message/popup 1784 is described abovewith reference to FIG. 15. The status information is continually updatedduring the process of making the call, but is not so limited.

When the call to cellular telephone 1799 is successfully connected bythe PBX, the MCS transfers 1720 the selected voice mail messages tocellular telephone 1799. Successful connection of the call causes statusmessage/popup 1784 to close. In contrast, when the call is notsuccessfully connected for any reason (e.g., error, line busy, noanswer, call not authorized, etc.), then a status message indicatingfailure of the call is displayed in popup 1784 along with the “close”button.

An ICS of an embodiment includes a system comprising at least one of amessaging server that receives messages, an interface that couples themessaging server to a network server and a client device of the network,a form-based user interface, wherein the messaging server causes a formincluding form data to be transferred to the client device via thenetwork, wherein execution of the form data generates the form-baseduser interface on the client device, and a communication couplingbetween the client device and at least one of the interface and themessaging server, wherein the form data controls communications betweenthe client device and the messaging server in response to at least oneuser selection via the form-based user interface, wherein thecommunication coupling is independent of the network.

A structure of the form of an embodiment is native to the network.

The form of an embodiment includes an embedded browser control for usein establishing the communication coupling.

The messaging server of an embodiment causes the form and form data tobe stored on a network server of the network. The messaging server of anembodiment transfers the form to the client device via the network. Theembedded browser control of the form of an embodiment establishes acoupling between the client device and at least one of the interface andthe messaging server.

The form-based user interface of an embodiment is transferable via anelectronic message from the network, the form-based interface enablingactions on at least one of user information and message information byusers of the client device. The message information of an embodimentincludes at least one of message contents and message description. Themessaging server of an embodiment caches at least one of the userinformation and the message information. The network of an embodimentstores at least one of the user information and the message information.The actions of an embodiment include routing a message, playing amessage, replying to a message, forwarding a message, generating anaudio call, modifying the user information.

The form-based user interface of an embodiment includes at least one ofa folder area, a contents area, and a tool bar. The system of anembodiment further comprises action buttons displayed in the tool bar,the action buttons controlling actions via the communication coupling onat least one of user information and message information. A subfolder ofthe folder area of an embodiment includes a uniform resource locator,wherein selection of the subfolder establishes the communicationcoupling with the messaging server. The form-based user interface of anembodiment further comprises a browser window that displays informationof the messages, wherein the uniform resource locator launches thebrowser window on a display area of the client device.

The form-based user interface of an embodiment further includes a popupwindow displayed at the client device via the communication coupling,the popup window displaying at least one of selection information andstatus information of the messages.

The type of the message of an embodiment includes at least one of avoice mail type, an email type, a multimedia messaging system type, aninstant messaging type, and a short messaging system type.

At least one of the messaging server and the interface of an embodimentfurther comprise a web server. The web server of an embodiment providesthe communication coupling with the client device independent of aconnection of the network.

The messaging server of an embodiment further comprises a plurality ofapplications including at least one voice application and at least onemobile application, wherein at least one voice browser couples theapplications to a communications exchange.

The network of an embodiment includes the network server coupled to adatabase and a communications network.

An ICS of an embodiment includes a system comprising at least one of: anetwork including a messaging system coupled to a database, a clientdevice, and a communications network; a messaging communication server(MCS) that couples to the network; an interface module that couples tothe MCS and the messaging system; a form-based user interface comprisingform data, wherein the messaging system generates the form data inresponse to a message received from the MCS, wherein the messagingsystem transfers the form data and information of the message to theclient device via the network; and a communication coupling between theclient device and at least one of the interface module and the MCS,wherein the communication coupling is independent of the network, theform data controlling the communication coupling in response to at leastone user selection via the form-based user interface.

An ICS of an embodiment includes a device comprising at least one of: amessaging server that receives messages; a form-based user interface(FBUI) that includes buttons, wherein the messaging server causes theFBUI to be transferred to a client device of a network using anelectronic message transmitted via a first coupling that is a couplingof the network; and a browser control embedded in the FBUI, wherein thebrowser control establishes a second coupling that couples the clientdevice and the messaging server, wherein the second coupling isindependent of the first coupling, the browser control transferringinformation of actions selected by a user via the buttons, wherein themessaging server applies the actions to at least one of user informationand information of the messages.

The information of the messages of an embodiment includes at least oneof message contents and message description.

The messaging server of an embodiment caches at least one of the userinformation and the information of the messages.

The network of an embodiment stores at least one of the user informationand the information of the messages.

The actions of an embodiment include routing a message, playing amessage, replying to a message, forwarding a message, generating anaudio call, modifying the user information.

The form-based user interface of an embodiment includes at least one ofa folder area, a contents area, and a tool bar.

A subfolder of the folder area of an embodiment includes a uniformresource locator, wherein selection of the subfolder establishes thesecond coupling. The form-based user interface of an embodiment furthercomprises a browser window that displays information of the messages,wherein the uniform resource locator launches the browser window on adisplay area of the client device.

The form-based user interface of an embodiment further includes a popupwindow displayed at the client device via the second coupling, the popupwindow displaying at least one of selection information and statusinformation of the messages.

A type of the messages of an embodiment includes at least one of a voicemail type, an email type, a multimedia messaging system type, an instantmessaging type, and a short messaging system type.

The messaging server of an embodiment further comprises a web server.

The components of the ICS described above include any collection ofcomputing components and devices operating together. The components ofthe ICS can also be components or subsystems within a larger computersystem or network. The ICS components can also be coupled among anynumber of components (not shown), for example other buses, controllers,memory devices, and data input/output (I/O) devices, in any number ofcombinations. Further, components of the ICS can be distributed amongany number/combination of other processor-based components.

Aspects of the ICS described herein may be implemented as functionalityprogrammed into any of a variety of circuitry, including programmablelogic devices (PLDs), such as field programmable gate arrays (FPGAs),programmable array logic (PAL) devices, electrically programmable logicand memory devices and standard cell-based devices, as well asapplication specific integrated circuits (ASICs). Some otherpossibilities for implementing aspects of the ICS include:microcontrollers with memory (such as electronically erasableprogrammable read only memory (EEPROM)), embedded microprocessors,firmware, software, etc. Furthermore, aspects of the ICS may be embodiedin microprocessors having software-based circuit emulation, discretelogic (sequential and combinatorial), custom devices, fuzzy (neural)logic, quantum devices, and hybrids of any of the above device types. Ofcourse the underlying device technologies may be provided in a varietyof component types, e.g., metal-oxide semiconductor field-effecttransistor (MOSFET) technologies like complementary metal-oxidesemiconductor (CMOS), bipolar technologies like emitter-coupled logic(ECL), polymer technologies (e.g., silicon-conjugated polymer andmetal-conjugated polymer-metal structures), mixed analog and digital,etc.

It should be noted that the various functions or processes disclosedherein may be described as data and/or instructions embodied in variouscomputer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of components and/or processesunder the ICS may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport refer to this application as a whole and not to any particularportions of this application. When the word “or” is used in reference toa list of two or more items, that word covers all of the followinginterpretations of the word: any of the items in the list, all of theitems in the list and any combination of the items in the list.

The above description of illustrated embodiments of the ICS is notintended to be exhaustive or to limit the ICS to the precise formdisclosed. While specific embodiments of, and examples for, the ICS aredescribed herein for illustrative purposes, various equivalentmodifications are possible within the scope of the ICS, as those skilledin the relevant art will recognize. The teachings of the ICS providedherein can be applied to other processing systems and methods, not onlyfor the systems and methods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the ICS in light of the above detailed description.

In general, in the following claims, the terms used should not beconstrued to limit the ICS to the specific embodiments disclosed in thespecification and the claims, but should be construed to include allprocessing systems that operate under the claims. Accordingly, the ICSis not limited by the disclosure, but instead the scope of the ICS is tobe determined entirely by the claims.

While certain aspects of the ICS are presented below in certain claimforms, the inventors contemplate the various aspects of the ICS in anynumber of claim forms. For example, while only one aspect of the ICS isrecited as embodied in machine-readable medium, other aspects maylikewise be embodied in machine-readable medium. Accordingly, theinventors reserve the right to add additional claims after filing theapplication to pursue such additional claim forms for other aspects ofthe ICS.

1. A system comprising: a messaging server that receives messages; aninterface that couples the messaging server to an email server of anemail system and a client device of the email system; a form-based userinterface, wherein the messaging server causes a form including formdata to be transferred to the client device via the email system,wherein execution of the form data generates the form-based userinterface on the client device; and a communication coupling between theclient device and at least one of the interface and the messagingserver, wherein the form data controls communications between the clientdevice and the messaging server in response to at least one userselection via the form-based user interface, wherein the communicationcoupling is independent of the email system.
 2. The system of claim 1,wherein a structure of the form is native to the email system.
 3. Thesystem of claim 1, wherein the form includes an embedded browser controlfor use in establishing the communication coupling.
 4. The system ofclaim 1, wherein the messaging server causes the form and form data tobe stored on an email server.
 5. The system of claim 4, wherein themessaging server transfers the form to the client device via the emailsystem.
 6. The system of claim 4, wherein an embedded browser control ofthe form establishes a coupling between the client device and at leastone of the interface and the messaging server.
 7. The system of claim 1,wherein the form-based user interface is transferable via an electronicmessage from the email system, the form-based interface enabling actionson at least one of user information and message information by users ofthe client device.
 8. The system of claim 7, wherein the messageinformation includes at least one of message contents and messagedescription.
 9. The system of claim 7, wherein the messaging servercaches at least one of the user information and the message information.10. The system of claim 7, wherein the email system stores at least oneof the user information and the message information.
 11. The system ofclaim 7, wherein the actions include routing a message, playing amessage, replying to a message, forwarding a message, generating anaudio call, modifying the user information.
 12. The system of claim 1,wherein the form-based user interface includes at least one of a folderarea, a contents area, and a tool bar.
 13. The system of claim 12,further comprising action buttons displayed in the tool bar, the actionbuttons controlling actions via the communication coupling on at leastone of user information and message information.
 14. The system of claim12, wherein a subfolder of the folder area includes a uniform resourcelocator, wherein selection of the subfolder establishes thecommunication coupling with the messaging server.
 15. The system ofclaim 14, wherein the form-based user interface further comprises abrowser window that displays information of the messages, wherein theuniform resource locator launches the browser window on a display areaof the client device.
 16. The system of claim 1, wherein the form-baseduser interface further includes a popup window displayed at the clientdevice via the communication coupling, the popup window displaying atleast one of selection information and status information of themessages.
 17. The system of claim 1, wherein a type of the messageincludes at least one of a voice mail type, an email type, a multimediamessaging system type, an instant messaging type, and a short messagingsystem type.
 18. The system of claim 1, wherein at least one of themessaging server and the interface further comprise a web server. 19.The system of claim 18, wherein the web server provides thecommunication coupling with the client device independent of aconnection of the email system.
 20. The system of claim 1, wherein themessaging server further comprises a plurality of applications includingat least one voice application and at least one mobile application,wherein at least one voice browser couples the applications to acommunications exchange.
 21. The system of claim 1, wherein the emailsystem includes the email server coupled to a database and acommunications network.
 22. A system comprising: a network including amessaging system coupled to a database, a client device, and acommunications network; a messaging communication server (MCS) thatcouples to the network; an interface module that couples to the MCS andthe messaging system; a form-based user interface comprising form data,wherein the messaging system generates the form data in response to amessage received from the MCS, wherein the messaging system transfersthe form data and information of the message to the client device viathe network; and a communication coupling between the client device andat least one of the interface module and the MCS, wherein thecommunication coupling is independent of the messaging system, the formdata controlling the communication coupling in response to at least oneuser selection via the form-based user interface.
 23. A devicecomprising: a messaging server that receives messages; a form-based userinterface (FBUI) that includes buttons, wherein the messaging servercauses the FBUI to be transferred to a client device of a network usingan electronic message transmitted via a first coupling that is acoupling of the network; and a browser control embedded in the FBUI,wherein the browser control establishes a second coupling that couplesthe client device and the messaging server, wherein the second couplingis independent of the first coupling, the browser control transferringinformation of actions selected by a user via the buttons, wherein themessaging server applies the actions to at least one of user informationand information of the messages.
 24. The device of claim 23, wherein theinformation of the messages includes at least one of message contentsand message description.
 25. The device of claim 23, wherein themessaging server caches at least one of the user information and theinformation of the messages.
 26. The device of claim 23, wherein thenetwork stores at least one of the user information and the informationof the messages.
 27. The device of claim 23, wherein the actions includerouting a message, playing a message, replying to a message, forwardinga message, generating an audio call, modifying the user information. 28.The device of claim 23, wherein the form-based user interface includesat least one of a folder area, a contents area, and a tool bar.
 29. Thedevice of claim 28, wherein a subfolder of the folder area includes auniform resource locator, wherein selection of the subfolder establishesthe second coupling.
 30. The device of claim 29, wherein the form-baseduser interface further comprises a browser window that displaysinformation of the messages, wherein the uniform resource locatorlaunches the browser window on a display area of the client device. 31.The device of claim 23, wherein the form-based user interface furtherincludes a popup window displayed at the client device via the secondcoupling, the popup window displaying at least one of selectioninformation and status information of the messages.
 32. The device ofclaim 23, wherein a type of the messages includes at least one of avoice mail type, an email type, a multimedia messaging system type, aninstant messaging type, and a short messaging system type.
 33. Thedevice of claim 23, wherein the messaging server further comprises a webserver.